WINMAIL.DAT â EVERLASTING PAIN
Dear
community,
I have a couple of users experiencing heavy impact on their daily work. What is happening:
A user receives an external email sent to all members of the team. The user replies, for example, to all in his turn and certain
internal recipients receive this reply without sender, without recipient, with empty body and winmail.dat as an attachment. When inspecting the header I can see that fields like “from”, “to” etc. are not present there at all (please
see the example below). To check the behavior we did the following
a.
Opened the original email
b.
Chose “reply to all”
c.
Checked the message format being HTML
d.
Sent the message
The message arrives again with no information excepting winmail.dat
Repeated the steps above, but with message format Text Only being chosen.
Same result, no sender, no recipient, no body, winmail.dat
Created a new message, copied whole content of the previous one, sent it again to all – in this case the message arrives
intact.
I can hardly understand why only few internal recipients are facing the problem and in the same time other recipients whose
mailboxes reside on the same mail server receive the very same messages with all information in place?
Here is my example:
Microsoft Mail Internet Headers Version 2.0
Received: ServerName.Domain.com ([192.168.5.18]) by ServerName.Domain.com with Microsoft SMTPSVC(6.0.3790.4675);
Tue, 24 May 2011 10:48:49
+0200
Content-Class: urn:content-classes:message
Subject: RE: DRAM demand E/May
MIME-Version: 1.0
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: binary
Date: Tue, 24 May 2011 10:48:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6619.12
Message-ID: <8D50446523C6D147AA8814C8B2E1718201049A31@ ServerName.Domain.com >
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <8D50446523C6D147AA8814C8B2E1718201049A31@ ServerName.Domain.com >
Thread-Topic: DRAM demand E/May
thread-index: AcwGS9a7LwFOoHd4QNWWk1rVQNbEiQAQf0UQAACTDTAAAINKYAAAYrTQABaiJbAAncYqkABGHcSwABzjfGAAQJVzsACMOkAgAAW26nAAA3L8kAAAY84wAAE8NEAAYSfMwAABR7
mAAASdogAALzYmkAACXhhgACLn69AAAEauEAAApLpAAABrHWAAAnmpkACUQ2UAAAaJFyAAABPskAADbixQAAS4G4AAJ3JpUAAH1KxQAF0BkdAALUlxsAAAZ74QAAAzK/AACc6+
YADBfMqw
References: <01af01cc064b$d74a8200$85df8600$%hippel@samsung.com> <DB5E471EFA085A49A89C31FB61332DA701566C53@ ServerName.Domain.com
> <02a501cc0690$c2013ca0$4603b5e0$%hippel@samsung.com> <DB5E471EFA085A49A89C31FB61332DA701566C5B@ ServerName.Domain.com > <02b301cc0693$ceacc4d0$6c064e70$%hippel@samsung.com> <DB5E471EFA085A49A89C31FB61332DA701566C5E@ ServerName.Domain.com>
<8D50446523C6D147AA8814C8B2E17182FAA773@ ServerName.Domain.com> <007101cc0a7f$33751fe0$9a5f5fa0$%hippel@samsung.com> <DB5E471EFA085A49A89C31FB61332DA701566EE5@ ServerName.Domain.com> <011801cc0bf4$6feb7750$4fc265f0$%hippel@samsung.com>
<DB5E471EFA085A49A89C31FB61332DA701566FD7@ ServerName.Domain.com> <00c101cc0e47$29cc3f20$7d64bd60$%hippel@samsung.com> <DB5E471EFA085A49A89C31FB61332DA701567044@ ServerName.Domain.com> <00ce01cc0e4b$8b71aa40$a254fec0$%hippel@samsung.com>
<DB5E471EFA085A49A89C31FB61332DA701567050@ ServerName.Domain.com> <009d01cc0fd5$98ceeb90$ca6cc2b0$%hippel@samsung.com> <"8D50446523C6D147AA88 A9C9"@d-f-
In all cases I have observed these messages either are originating from Asia or were already sent to Asia
and returned as reply. The header of all messages involved contains the references similar as in the example above. Even when using OWA there is no chance to see who have sent the message and what was in it. Please help.
Thank you
Eduard
May 25th, 2011 8:51am
Unfortunately, as I already mentioned in the original post, I did it myself personally.
I opened the original message, clicked Reply to All and than changed the format into PLAIN TEXT
(Text only) and, nevertheless, the message arrived empty and with the winmail.dat attachment. This is exatly what makes the whole thing so weird.
On the other hand, we can not afford sending plain text only as the messages contain additional information, embedded images and so on. We rely on sending HTML messages.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 6:15am
Unfortunately, as I already mentioned in the original post, I did it myself personally.
I opened the original message, clicked Reply to All and than changed the format into PLAIN TEXT
(Text only)and, nevertheless, the message arrived emty and with the winmail.dat attachment. This is exatly what makes the whole thing so weird.
On the other hand, we can not afford sending plain text only as the messages contain additional information, embedded images and so on. We rely on sending HTML messages.
May 26th, 2011 6:22am
Yes, accordning to all information I was able to find, HTML messages should not produce winmail.dat, but this ís exactly what is happening in my case. When replying I ensured myself that HTML is chosen, but this did not changed the behavour. Chosing
Text Only did not as well.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 6:32am
Thank you John, this looks like a good idea. I have changed the golbal settings a few minutes ago and will observe whether it helps.
May 26th, 2011 6:34am